What's New in 12.2.0

Requirement History now Captured for all Rule-Based Additions and Updates

OIPA has been enhanced to provide a more complete history of requirement changes. History records are now created not only when requirements are added or updated through the user interface, but also when changes occur through attached business rules, such as AddRequirements, ProcessRequirements, and CopyToRequirementFields, during activity or requirement processing.

Key Updates:

  • Comprehensive Requirement Tracking: All changes to requirements, regardless of whether they are made manually in the UI or automatically by business rules, are now logged and available for review.

  • History Tab: Users can now view a detailed history of requirement operations directly from the History tab on the client requirement screen.

  • Security Management: Access to requirement history information can be managed by administrators through the new ClientRequirementHistory security page in Rules Palette.

These enhancements ensure improved traceability and transparency for all requirement-related operations in OIPA.

Enhanced Requirement Deletion Control

OIPA now enables more flexible and controlled deletion of requirements when reversing or recycling activities.

Key enhancements:

  • DeleteRequirements Business Rule:

    A new configurable rule allows organizations to define which requirements should be set to “DELETED” status when a parent activity or requirement is reversed or recycled. Options include:

    • Deleting all generated child requirements,

    • Deleting only specific requirements, or

    • Applying conditional logic to fine-tune deletion behavior.

  • Improved Hierarchy Management:The deletion process can now be precisely controlled at each level of the requirement hierarchy, preventing unintended deletion of requirements in subsequent generations unless explicitly allowed by configuration.

  • Requirement Screen Enhancement:Requirements with a “DELETED” status can now be viewed and filtered on the requirements screen, enabling users to manage and review deleted records as needed.

  • History Tracking: All changes to requirement statuses, including deletions, are captured and displayed in the requirements’ history tab for complete traceability.

Activity Requirement Table Enhancement

Before this enhancement, the requirement table in the Activity requirement screen does not have the sort option for columns, and users could not select requirement statuses from a relevant list.

With this enhancement:

  • You can now sort Status column in the Requirement table of Activity Requirement screen.

  • By default, the requirement table sorts entries by last modified and creation date. You can sort the columns as per your requirement.

Note: If requirement level does not configure specific statuses, the system shows all standard statuses instead.

 

Show or Hide for Inquiry Screen Result Tabs using ScreenMath Configuration

With this enhancement, user can now configure InquiryScreen Result tabs in OIPA to dynamically show or hide based on ScreenMath configuration using a new SHOW attribute. This allows tabs to appear conditionally in response to user actions or business rules, improving usability and keeping screens relevant. Existing configurations are unaffected unless this feature is explicitly configured.

Restore Requirement Statuses on Activity Reversal for ProcessRequirements

When an Activity is reversed, OIPA now also restores the Requirement statuses that were updated by ProcessRequirements during the original Activity processing.

Addition of attributes to INQUIRYSCREEN Business rule

The Inquiry screen on OIPA now allows Inquiry results to refresh automatically whenever the user chooses a different option on a configured dropdown field. This new functionality loads the results section when you change the dropdown (Combo) values, if configured. These updates help you get to the information you need faster, with fewer clicks.

SUBMITFORM

  • This attribute if configured, allows the screen to automatically refresh the results when you change a selected configured dropdown field values.

  • It works just like clicking the OK button, but the system does it for you

  • If not configured, the screen continues to work as before.

FIELD

  • This attribute only works if configured with SUBMITFORM attribute, and it identifies the specific dropdown (Combo) field that will refresh the results tab on user action.

  • Only drop-down Combo fields can be used for this behavior.

  • It works together with SUBMITFORM to ensure the right field triggers the updated results.

Inquiry results now load instantly when you change certain dropdown selections, giving you fewer clicks, faster navigation, and the continued option to use the OK button whenever needed.

History Logging for API-Driven Updates

OIPA Service APIs have been enhanced to support auditability by recording API-driven create or update changes in the same history tables used for manual UI updates. History records are written only after successful API responses, while failed attempts are captured separately for operational accountability. A new UpdateSource indicator (M=Manual, A=API) is added to history tables to clearly identify how a change was made. Additionally, a new AsRestServiceErrors table logs failed API attempts such as 400, 401, and 403 with encrypted request payloads and masked client IP information.